Apparatus and Methods for Decoupling an Uplink Enhanced Dedicated Channel and High Speed Downlink Shared Channel

ABSTRACT

Apparatus and Method for Decoupling an Uplink Enhanced Dedicated Channel and High Speed Downlink Shared Channel A method in a network node for decoupling an uplink enhanced dedicated channel, E-DCH, and a high speed downlink shared channel, HS-DSCH, comprises determining whether a radio link message contains a E-DCH decoupling indication (step  201 ). Where it is determined that the radio link message does not contain an E-DCH decoupling indication, the method comprises controlling a base station node to reject a radio link procedure in the event that a serving E-DCH radio link and a serving HS-DSCH radio link are not configured in the same cell (step  203 ).

TECHNICAL FIELD

Embodiments described herein relate generally to wirelesscommunications, and more particularly to apparatus and methods fordecoupling an uplink enhanced dedicated channel and a high speeddownlink shared channel.

BACKGROUND

Certain standards provide specifications for cellular telecommunicationsnetwork technologies, including radio access, the core transportnetwork, and service capabilities. For example, Release 12 of the 3rdGeneration Partnership Project (3GPP) provides enhanced support ofHeterogeneous Networks for co-channel, dedicated frequency, andmulticarrier. One objective is to avoid co-channel interference, forexample by specifying solutions to mitigate uplink and downlinkimbalance. In view of this, one aspect of the enhanced support is toallow an uplink enhanced dedicated channel (E-DCH) to be decoupled forRel-12 terminals. E-DCH decoupling in this context is the decoupling ofthe serving E-DCH cell and the serving high speed downlink sharedchannel (HS-DSCH) cell from each other. Doing so can improve theperformance in the presence of imbalance between the uplink and thedownlink, characteristic to the heterogeneous network environment.

In the Radio Link resources handling, the E-DCH and the HS-DSCH may besetup, added, and/or reconfigured separately, using Radio Link Setup,Radio Link Addition and/or Radio Link Reconfiguration procedures andassociated radio link messages.

In the current Node B Application Part (NABP) and the Radio NetworkSubsystem Application Part (RNSAP) specifications, the establishment ofan E-DCH on one or more radio links are supported. The Serving E-DCHRadio Link Information Element, “Serving E-DCH RL IE” may be used forexample to indicate the Serving E-DCH RL.

However, the existing 3GPP standard (i.e. pre-Release 12 of the 3GPPstandard) specifies that, if the serving E-DCH and the serving HS-DSCHare not in the same cell, the node B or the drifting network radiocontroller (DRNC) should reject the radio link resource handlingprocedures, and as such do not support a decoupling procedure.

For example, the legacy procedures couple the serving E-DCH and HS-DSCH,as shown from the extract below from 3GPP Technical Specification TS25.433 (pre Release 12), for example the Abnormal Conditions accordingto section 8.2.17.4 which relate to a Radio Link Setup Requestprocedure, and which states:

If the RADIO LINK SETUP REQUEST message contains the HS-PDSCH RL ID IEand the Serving E-DCH RL IE but the Serving HS-DSCH Radio Link and theServing E-DCH Radio Link are not configured to be in the same cell thenthe Node B shall reject the procedure using the RADIO LINK SETUP FAILUREmessage.

Thus, from above it can be seen that the current (Pre Release 12) 3GPPspecifications relating to NABP or RNSAP do not permit decoupling, whichresults in a backwards compatibility problem between a radio networkcontroller (RNC) configured for Release 12 or later, and pre-Release 12Node Bs and DRNCs.

SUMMARY

It is an aim of the embodiments of the present disclosure to provide amethod and apparatus which obviate or reduce at least one or more of thedisadvantages mentioned above.

According to a first aspect, there is provided a method in a networknode for decoupling an uplink enhanced dedicated channel, E-DCH, and ahigh speed downlink shared channel, HS-DSCH. The method comprisesdetermining whether a radio link message contains a E-DCH decouplingindication. Where it is determined that the radio link message does notcontain an E-DCH decoupling indication, the method comprises controllinga base station node to reject a radio link procedure in the event that aserving E-DCH radio link and a serving HS-DSCH radio link are notconfigured in the same cell.

According to another aspect, there is provided a radio network node fordecoupling an uplink enhanced dedicated channel, E-DCH, and a high speeddownlink shared channel, HS-DSCH. The radio network node comprises anetwork interface adapted to interface with a radio network, a memoryunit and a processor unit. The processor unit is adapted to run programinstructions stored on the memory unit. The processor unit is adapted todetermine whether a radio link message received from a radio networkcontroller, RNC, contains an indication that a radio link procedure hasthe capability of decoupling an E-DCH and a HS-DSCH. Where it isdetermined that the radio link message does not contain an E-DCHindication, the processor unit is further adapted to reject the radiolink procedure in the event that a serving E-DCH radio link and aserving HS-DSCH radio link are not configured in the same cell.

According to another aspect, there is provided a radio networkcontroller, RNC, node for decoupling an uplink enhanced dedicatedchannel, E-DCH, and a high speed downlink shared channel, HS-DSCH. Theradio network controller node comprises a network interlace adapted tointerlace with a radio network, a memory unit and a processor unit. Theprocessor unit is adapted to run program instructions stored on thememory unit. The processor unit is adapted to determine whether areceived radio link message contains a E-DCH decoupling indication,indicating that a base station node supports decoupling of an E-DCH anda high speed downlink shared channel, HS-DSCH. Where it is determinedthat the E-DCH decoupling indication has not been received, theprocessor unit is further adapted to control the base station node toreject the radio link procedure in the event that a serving E-DCH radiolink and a serving HS-DSCH radio link are not configured in the samecell.

According to another aspect, there is provided a method comprising thesteps of inserting an information element into a radio link message, theinformation element comprising an indication that an uplink enhanceddedicated channel, E-DCH, may be decoupled from a high speed downlinkshared channel, HS-DSCH.

Some embodiments propose solutions to solve the backwards not compatibleproblem caused by decoupling an uplink enhanced dedicated channel(E-DCH) cell and a high speed downlink shared channel (HS-DSCH) cellfrom each other. In one example embodiment, the method may include:

Determining whether an RNC has received an indication stating that aNode B or DRNC supports EDCH decoupling;

Applying pre Rel-12 Abnormal Conditions, where it is determined that theindication has not been received from the Node B or DRNC; and

Not applying pre Rel-12 Abnormal Conditions, where it is determined thatthe indication has been received from the Node B or DRNC.

Optionally, the indication from Node B may be set on Cell bases and beincluded in Audit and Resource Status Indication procedure.

Optionally, the indication from Node B may be added to an existing NodeB Cell Capability Container, which is sent in AUDIT.

In another example embodiment, the method may include;

Determining whether an RNC has transmitted a message to the Node B orDRNC indicating that the radio link is setup with decoupled E-DCH andthe Node B or DRNC has accepted to support E-DCH decoupling;

Applying pre Rel-12 Abnormal Conditions, where it is determined that theRNC has not transmitted the message to the Node B or DRNC indicatingthat the radio link is setup with decoupled E-DCH and/or the Node B orDRNC has not accepted to support E-DCH decoupling; and

Not applying pre Rel-12 Abnormal Conditions, where it is determined thatRNC has transmitted the message and the Node B or DRNC has accepted tosupport E-DCH decoupling.

In still another example embodiment, the method may include:

Determining whether 1) an ANC has transmitted a message to the Node B orDRNC indicating that the radio link is setup with decoupled E-DCH and 2)the Node B or DRNC has transmitted an indication stating that the Node Bor DRNC supports E-DCH decoupling;

Applying pre Rel-12 Abnormal Conditions, where it is determined that theRNC has not transmitted the message to the Node B or DRNC and that theNode B or DRNC has not transmitted the message indicating that itsupports E-DCH decoupling; and

Not applying pre Rel-12 Abnormal Conditions, where it is determined thatthe RNC has transmitted the message to the Node B or DRNC and that theNode B or DRNC has transmitted the message indicating that it supportsE-DCH decoupling.

-   Other implementations may include a wireless communication device    and/or access node configured to implement the described method, or    a wireless communication system in which a wireless communication    device and/or access node implement the described method.

Some embodiments of the disclosure may provide one or more technicaladvantages. For example, in certain embodiments, decoupling of theserving E-DCH cell and the serving HS-DSCH cell may be allowed for theimproved performance in the presence of imbalance between the uplink andthe downlink. Accordingly, a technical advantage may be the decouplingof the serving E-DCH cell and the serving HSDSCH cell in heterogeneousnetwork environments. Another technical advantage may be that the Node Bor DRNC may not reject a particular radio link procedure even where theHS-DSCH and the E-DCH are not in the same cell. Still another advantagemay be that the backwards not compatible problem may be alleviated. Someembodiments may benefit from some, none, or all of these advantages.Other technical advantages may be readily ascertained by one of ordinaryskill in the art.

BRIEF DESCRIPTION OF DRAWINGS

For a more complete understanding of the present invention and itsfeatures and advantages, reference is now made to the followingdescription, taken in conjunction with the accompanying drawings, inwhich:

FIG. 1 is a block diagram illustrating an embodiment of a network;

FIG. 2a illustrates a method according to an embodiment:

FIG. 2b illustrates a method according to another embodiment;

FIG. 2c illustrates a method according to another embodiment;

FIG. 3a illustrates a method according to another embodiment;

FIG. 3b illustrates a method according to another embodiment;

FIG. 4 illustrates a method according to another embodiment;

FIG. 5 is a block diagram illustrating certain embodiments of a radionetwork node: and

FIG. 6 is a block diagram illustrating certain embodiments of anotherradio network node.

DETAILED DESCRIPTION

Particular embodiments are described in FIGS. 1-6 of the drawings, likenumerals being used for like and corresponding parts of the variousdrawings.

A radio network controller may facilitate a communication session for awireless device in soft handover with an active set of cells. The activeset may include a serving cell and one or more non-serving cells. FIG. 1is a block diagram illustrating embodiments of a radio network 100 thatincludes one or more wireless devices 110, radio network nodes 115 (forexample base station nodes), radio network controller 120, and corenetwork nodes 130. A wireless device 110 may communicate with a radionetwork node 115 over a wireless interface. For example, wireless device110 may transmit wireless signals to radio network node 115 and/orreceive wireless signals from radio network node 115. The wirelesssignals may contain voice traffic, data traffic, control signals, and/orany other suitable information.

Radio network node 115 may interface with radio network controller 120,Radio network controller 120 may control radio network node 115 and mayprovide certain radio resource management functions, mobility managementfunctions, and/or other suitable functions. Radio network controller 120may interface with core network node 130. In certain embodiments, radionetwork controller 120 may interface with core network node 130 via aninterconnecting network. The interconnecting network may refer to anyinterconnecting system capable of transmitting audio, video, signals,data, messages, or any combination of the preceding. The interconnectingnetwork may include all or a portion of a public switched telephonenetwork (PSTN), a public or private data network, a local area network(LAN), a metropolitan area network (MAN), a wide area network (WAN), alocal, regional, or global communication or computer network such as theInternet, a wireline or wireless network, an enterprise intranet, or anyother suitable communication link, including combinations thereof.

In some embodiments, core network node 130 may manage the establishmentof communication sessions and various other functionality for wirelessdevice 110. Wireless device 110 may exchange certain signals with corenetwork node 130 using the non-access stratum layer. In non-accessstratum signalling, signals between wireless device 110 and core networknode 130 may be transparently passed through the radio access network.Example embodiments of a radio network node 115, and a network node(such as radio network controller 120 or core network node 130) aredescribed later with respect to FIGS. 5 and 6, respectively.

FIG. 2a shows a method, according to one embodiment, in a network nodefor decoupling an uplink enhanced dedicated channel, E-DCH, and a highspeed downlink shared channel, HS-DSCH. The method comprises determiningwhether a radio link message contains a E-DCH decoupling indication,step 201. Where it is determined that the radio link message does notcontain an E-DCH decoupling indication, a base station node iscontrolled to reject a radio link procedure in the event that a servingE-DCH radio link and a serving HS-DSCH radio link are not configured inthe same cell, step 203.

In one example, where it is determined that the radio link message doescontain an E-DCH decoupling indication, a base station node iscontrolled such that it does not reject a radio link procedure in theevent that a serving E-DCH radio link and a serving HS-DSCH radio linkare not configured in the same cell.

The E-DCH decoupling indication may be provided in an informationelement, IE, of the radio link message. In one example this may bereferred to as an E-DCH Decoupling Indication IE.

In one embodiment the E-DCH decoupling indication may be set on a percell basis. The E-DCH decoupling indication may be included, forexample, in an audit and resource status indication procedure, forexample as defined in the third generation partnership project, 3GPP,Technical Specification TS 25.433 (e.g. v.12.0.0 or later), sections8.2.7 and 8.2.15, respectively. In one example the E-DCH decouplingindication may be added to a cell capability container, for example anexisting cell capability container.

The base station node may comprise, for example, a Node B or a driftingradio network controller, DRNC, node.

According to some embodiments a radio link procedure may comprise aradio link setup request procedure, a radio link addition requestprocedure, a radio link reconfiguration prepare procedure or a radiolink reconfiguration request procedure.

According to some embodiments a radio link message may comprise a radiolink setup request message, a radio link addition request message, aradio link reconfiguration prepare message or a radio linkreconfiguration request message.

The method may comprises performing abnormal conditions relating to oneor more of sections 8.2.17.4 or 8.3.1.4 or 8.3.2.4 or 8.3.5.4 of thethird generation partnership project, 3GPP, Technical Specification TS25.433 version 12.0.0 or later.

In one embodiment, at least part of the method may be performed in anetwork node comprising a radio network controller, RNC, node. In suchan embodiment the E-DCH decoupling indication may be received from abase station node, i.e. a base station node which is to be controlled.

In one embodiment, at least part of the method may be performed in anetwork node comprising a base station node, for example a Node B orDRNC. In such an embodiment, the E-DCH decoupling indication may bereceived from a radio network controller, RNC node.

In one example the base station node may perform the step of decidingwhether or not to support E-DCH decoupling. The step of deciding whetheror not to support E-DCH decoupling may be based on one or more of:whether the base station node is capable of supporting decoupling of anE-DCH and a HS-DSCH; whether the base station node is capable ofsupporting decoupling of an E-DCH and a HS-DSCH, and if so, whether thebase station node wishes to provide decoupling for that particular radiolink based on some other criteria; whether the base station node iscapable of supporting decoupling of an E-DCH and a HS-DSCH, and if so,whether the base station node has capacity to support E-DCH decoupling.

FIG. 2b illustrates a method according to another embodiment, fordecoupling an uplink enhanced dedicated channel (E-DCH) cell and a highspeed downlink shared channel (HS-DSCH) cell that solves the backwardsnot compatible problem. At step 202, a network node, for example a basestation node, such as a Node B or DRNC, indicates to a Radio NetworkController (RNC) that it can handle the E-DCH decoupling. According tothis embodiment, the RNC is configured such that it may only setup thedecoupled E-DCH towards this type of Node B or DRNC, e.g. towards a basestation node which has indicated in this manner that it supportsdecoupling of the E-DCH.

According to one embodiment, an explicit indication is sent from a NodeB or DRNC to a RNC to state that it supports the decoupled E-DCH. Thisindication may be set on a per cell basis, for example whereby each cellreports its capability separately, e.g. on a cell-by-cell basis. Theindication may be included in Audit and Resource Status indicationprocedures in certain embodiments. For example, such an indication maybe added to an existing Node B Cell Capability Container, which is sentin AUDIT. At step 204, it is determined whether the radio link handlingmessage from the Node B indicates that it supports E-DCH decoupling. Inparticular embodiments, the Abnormal Conditions in specificationsrelating to the Node B Application Part (NBAP) or the Radio NetworkSubsystem Application Part (RNSAP) in Radio Link Setup, Radio LinkAddition, Radio Link Reconfiguration procedures may be modified to statethat, if the Node B does not indicate the E-DCH decoupling, then theexisting abnormal condition is valid.

Table 1 below is an extract from Technical Specification TS 25.433 (v.12.0.0), 8.2.17.4 Abnormal Conditions. The text shown in bolddemonstrates alternative language according to one embodiment, forrealising the procedure described above for FIG. 2a or 2 b:

TABLE 1 Current Text Modified Text Example 8.2.17.4 If the RADIO LINKSETUP If the Node B does not Abnormal REQUEST message indicate “E-DCHdecoupling Conditions contains the HS-PDSCH Capable”, and if the RADIORL ID IE and the Serving LINK SETUP REQUEST E-DCH RL IE but the messagecontains the HS- Serving HS-DSCH Radio PDSCH RL ID IE and the Link andthe Serving E- Serving E-DCH RL IE but the DCH Radio Link are notServing HS-DSCH Radio Link configured to be in the and the Serving E-DCHRadio same cell then the Node B Link are not configured to be shallreject the procedure in the same cell then the Node using the RADIO LINKB shall reject the procedure SETUP FAILURE using the RADIO LINK SETUPmessage. FAILURE message.

As can be seen from TABLE 1, according to pre-Rel 12 abnormalconditions, if a Radio Link Setup Request message contains a High SpeedPhysical Downlink Shared Channel Radio Link Identifier InformationElement (HS-PDSCH RL ID IE) and the serving Enhanced Uplink DedicatedChannel Radio Link Information Element (E-DCH RL IE), but the servingHS-DSCH radio link and the serving E-DCH radio link are not configuredto be in the same cell, then the Node B shall reject the procedure usingthe radio link setup failure message.

In this example, a new information element, IE, is introduced, which asmentioned earlier may be referred to as the “E-DCH decouplingcapability” information element, which can be set to “E-DCH decouplingCapable” and “E-DCH decoupling Not Capable”. Thus, where an indicationhas not been received indicating that it supports E-DCH decoupling, thepre-Release 12 Abnormal Conditions may be applied (shown as step 205).

Conversely, if RNC determines that it has received such a notificationfrom Node B, the pre-Rel 12 Abnormal Conditions are not applied at astep 206. This embodiment allows the E-DCH decoupling in a very generalway. The change allows not only the decoupling for macro and low powernode (Macro-LPN) deployment, but also any other legacy deployment,according to certain embodiments.

FIG. 2c shows a method in a network node according to anotherembodiment, for decoupling an uplink enhanced dedicated channel, E-DCH,and a high speed downlink shared channel, HS-DSCH. The method comprisesdetermining whether a radio network controller, RNC, has received anindication stating that a base station node supports decoupling an E-DCHand a HS-DSCH, step 208. Where it is determined that an indication hasnot been received from the base station, the method comprises applyingabnormal conditions relating to pre-release 12 of 3GPP, i.e. applyingpre- Rel 12 Abnormal Conditions, step 210. Where it is determined thatan indication has been received from the base station, the methodcomprises not applying abnormal conditions relating to pre-release 12 of3GPP, i.e. not applying pre Rel-12 Abnormal Conditions, step 212.

In one example, the indication from the base station node is set on aper cell basis. The indication from the base station may be included inan audit and resource status indication procedure.

In one example the indication from the base station may be added to abase station cell capability container, for example an existing cellcapability container, which is sent in an audit procedure.

According to certain embodiments, the base station node comprises a NodeB or a drifting network radio controller, DRNC, node.

FIG. 3a illustrates an alternative method for decoupling an E-DCH celland a HS-DSCH cell from each other, in accordance with certain otherembodiments. According to the illustrated method, the RNC indicates thatthe Radio Link is setup with decoupled E-DCH at step 302. Specifically,in one example the EDCH decoupling indication is sent from the RNC to abase station node, for example a Node B or DRNC, to indicate the E-DCHis decoupled from HS-DSCH. For example, such an indication can be addedin the dedicated Radio Link messages (for example Radio Link SetupRequest, Radio Link Addition Request, Radio Link ReconfigurationPrepare, Radio Link Reconfiguration Request).

For the base station node (e.g. Node B or DRNC) that can supportdecoupling, and wishes to handle decoupling, the base station node canaccept the messages and set up so that the serving E-DCH and the servingHS-DSCH are not necessarily in the same cell. Subsequently, adetermination can be made at step 304 that the Node B or DRNC hasaccepted the message, and that the pre-Rel 12 Abnormal Condition willnot be applied at step 306. As such, when a base station node is capableof supporting decoupling (and wishes to use decoupling for thatparticular radio link setup, for example based on some form ofpredetermined criteria), then the base station node may allow the E-DCHand HS-DSCH to be decoupled.

In particular embodiments, the Abnormal Conditions in NBAP/RNSAPspecifications in Radio Link Setup, Radio Link Addition, Radio LinkReconfiguration procedures may be modified to state if RNC does notindicate E-DCH decoupling, then the existing abnormal condition isvalid. Table 2a is an extract from TS 25.433 (v. 12.0.0) 8.2.17.4Abnormal Conditions and demonstrates proposed alternative language forthis type of embodiment:

TABLE 2a Current Text Modified Text Example 8.2.17.4 If the RADIO LINKSETUP If the RADIO LINK SETUP Abnormal REQUEST message REQUEST messagedoes not Conditions contains the HS-PDSCH contain E-DCH decoupling RL IDIE and the Serving Request IE and contains the E-DCH RL IE but theHS-PDSCH RL ID IE and the Serving HS-DSCH Radio Serving E-DCH RL IE butthe Link and the Serving E- Serving HS-DSCH Radio Link DCH Radio Linkare not and the Serving E-DCH Radio configured to be in the Link are notconfigured to be same cell then the Node B in the same cell then theNode shall reject the procedure B shall reject the procedure using theRADIO LINK using the RADIO LINK SETUP SETUP FAILURE FAILURE message.message.

In particular embodiments, the Abnormal Conditions in NBAP/RNSAPspecification in Radio Link Setup, Radio Link Addition, Radio LinkReconfiguration procedures may be modified to state if RNC does notindicate E-DCH decoupling, then the existing abnormal condition isvalid. Table 2b is an extract from TS 25.433 (v. 12.0.0) 8.2,17.4Abnormal Conditions and demonstrates proposed alternative language forthis type of embodiment:

TABLE 2b Current Text Modified Text Example 8.2.17.4 If the RADIO LINKSETUP If the RADIO LINK SETUP Abnormal REQUEST message REQUEST messagedoes not Conditions contains the HS-PDSCH contain the E-DCH RL ID IE andthe Serving Decoupling Indication IE but E-DCH RL IE but the containsthe HS-PDSCH RL Serving HS-DSCH Radio ID IE and the Serving E-DCH Linkand the Serving E- RL IE, and

 the Serving DCH Radio Link are not HS-DSCH Radio Link and theconfigured to be in the Serving E-DCH Radio Link are same cell then theNode B not configured to be in the shall reject the procedure same cellthen the Node B using the RADIO LINK shall reject the procedure SETUPFAILURE using the RADIO LINK SETUP message. FAILURE message.

This alternative (covered by the examples of Tables 2a and 2b) allowsthe E-DCH decoupling to be applied on a per user equipment (UE) basis.

Furthermore, a base station node (e.g. Node B) may allow/disallow theE-DCH decoupling on a case by case basis (i.e. from one radio link setupto another radio link setup, or from one radio link addition to another,or from one radio link reconfiguration to another), for example based onsome predetermined criteria. The criteria may include, for example, ascenario where a base station node has a missing capability, or aresource shortage, or a hardware failure. Other criteria may also beused.

Such embodiments provide both flexibility in the radio networkcontroller and in the base station node. For a Node B or DRNC that didnot accept the message of step 302 (or does not support decoupling), theabnormal conditions according to the current specification can beapplied (i.e. the pre-Rel 12 Abnormal Conditions applied, as shown instep 308), and hence the decoupling procedure will be rejected. Inparticular embodiments, a failure cause can be introduced to theNBAP/RNSAP specification such that when a Node B or DRNC rejects theprocedure due to not supporting or not allowing E-DCH decoupling, thecause value is sent to the RNC in the failure message.

FIG. 3b shows a method in a base station node according to anotherembodiment, for decoupling an uplink enhanced dedicated channel, E-DCH,and a high speed downlink shared channel, HS-DSCH. The method comprisesdetermining whether a message has been received from a radio networkcontroller, RNC, indicating that a radio link is setup with thecapability of decoupling an E-DCH and a HS-DSCH, step 310. In step 312,it is decided whether to support E-DCH decoupling. Where it isdetermined that a message has not been received from the RNC indicatingthat the radio link is setup with a decoupled E-DCH capability, and/orthe base station node has decided not to support E-DCH decoupling, instep 314 the method comprises applying abnormal conditions relating topre-release 12 of 3GPP, i.e. applying pre Rel-12 Abnormal Conditions.Where it is determined that a message has been received from the RNCindicating that the radio link is setup with a decoupled E-DCHcapability, and the base station node has decided to support E-DCHdecoupling, the method comprises in step 316 not applying abnormalconditions relating to pre-release 12 of 3GPP, i.e. not applying preRel-12 Abnormal Conditions.

In one example the step of deciding whether or not to support E-DCHdecoupling is based on whether the base station node is capable ofsupporting decoupling of an E-DCH and a HS-DSCH. In another example, thestep of deciding whether or not to support E-DCH decoupling is based onwhether the base station node is capable of supporting decoupling of anE-DCH and a HS-DSCH, and if so, whether the base station node wishes toprovide decoupling for that particular radio link based on some othercriteria.

Although FIGS. 2a to 2c and 3a to 3b are described as relating toalternative methods for decoupling an E-DCH cell and a HS-DSCH cell fromeach other, it is possible to combine the solutions proposed in any ofFIGS. 2a to 2c and 3a to 3b . In such an embodiment, an explicitindication may be sent from a Node B or DRNC to a RNC to state that itsupports the decoupled E-DCH. Additionally, the E-DCH decouplingindication may be sent from a RNC to a Node B or DRNC to indicate theE-DCH is decoupled from HS-DSCH.

FIG. 4 shows an example of a method according to a combined embodiment.

In step 401 it is determined whether a Node B indicates E-DCH decouplingcapability. If not, the method comprises the step of applying abnormalconditions relating to pre-release 12 of 3GPP, i.e. applying pre-Rel 12Abnormal Conditions, step 405. If it is determined in step 401 that theNode B does indicate E-DCH decoupling capability, it is determined instep 403 if the ANC indicates E-DCH decoupling capability. If not, themethod comprises the step of applying abnormal conditions relating topre-release 12 of 3GPP, i.e. applying pre-Rel 12 Abnormal Conditions,step 405. If it is determined in step 403 that the RNC does indicateE-DCH decoupling capability, the method comprises the step of notapplying abnormal conditions relating to pre-release 12 of 3GPP, i.e.not applying pre-Rel 12 Abnormal Conditions, step 407. It is noted thatin the embodiment above, steps 401 and 403 may be performed in anyorder.

In particular embodiments that combine the methods of FIGS. 2a to 2c and3a to 3b , for example an embodiment that performs the steps of FIG. 4above, the Abnormal Conditions in NBAP/RNSAP specification in Radio LinkSetup, Radio Link Addition, Radio Link Reconfiguration procedures may bemodified to state if the RNC does not indicate E-DCH decoupling or ifNode B does not indicate its E-DCH decoupling support, then the existingabnormal condition is valid. Table 3 below is an extract from TS 25.433(v. 12 •0 •0)/82.17.4 Abnormal Conditions and demonstrates proposedalternative language for such an embodiment:

TABLE 3 Current Text Modified Text Example 8.2.17.4 If the RADIO LINKSETUP If the Node B does not Abnormal REQUEST message indicate “E-DCHdecoupling Conditions contains the HS-PDSCH Capable”, and if the RADIORL ID IE and the Serving LINK SETUP REQUEST E-DCH RL IE but the messagedoes not contain E- Serving HS-DSCH Radio DCH decoupling Request IE Linkand the Serving E- and contains the HS-PDSCH DCH Radio Link are not RLID IE and the Serving E- configured to be in the DCH RL IE but theServing same cell then the Node B HS-DSCH Radio Link and the shallreject the procedure Serving E-DCH Radio Link are using the RADIO LINKnot configured to be in the SETUP FAILURE same cell then the Node Bmessage. shall reject the procedure using the RADIO LINK SETUP FAILUREmessage.

This alternative provides flexibility in a RNC and a Node L or DRNC.

Although the examples described in Tables 1, 2a, 2b and 3 are made inthe context of Radio Link Setup Request procedures and messages, and the

Abnormal Conditions according to section 8.2.17.4 of TS 25.433, v.12.0.0or later, it is noted that the embodiments may also be applied to theRadio Link Addition Request procedures and message, and thecorresponding Abnormal Conditions according to section 8.3.1.4 of TS25,433, v.12.0,0 or later. In such an example the Abnormal Conditionsmay be adapted as follows:

If the RADIO LINK ADDITION REQUEST message does not contain the E-DCHDecoupling Indication IE but contains the HS-PDSCH RL ID IE [FDD—in theHS-DSCH Serving Cell Change Information IE] and/or Serving E-DCH RL IE,and if both HS-DSCH and E-DCH are configured in the Node B but theServing HS-DSCH Radio Link and the Serving E-DCH Radio Link are not inthe same cell, then the Node B shall reject the procedure using theRADIO LINK ADDITION FAILURE message.

It is noted that the embodiments may also be applied to the Radio LinkReconfiguration Prepare procedures and message, and the correspondingAbnormal Conditions according to section 8.3.2.4 of TS 25.433, v.12.0.0or later. In such an example the Abnormal Conditions may be adapted asfollows:

If the RADIO LINK RECONFIGURATION PREPARE message does not contain theE-DCH Decoupling Indication IE but contains the HS-PDSCH RL ID IE and/orthe Serving E-DCH RL IE, and if both HS-DSCH and E-DCH are configured inthe new configuration but the Serving HS-DSCH Radio Link and the ServingE-DCH Radio Link are not in the same cell, then the Node B shall rejectthe procedure using the RADIO LINK RECONFIGURATION FAILURE message.

It is noted that the embodiments may also be applied to the Radio LinkReconfiguration Request procedures and message, and the correspondingAbnormal Conditions according to section 8.3.5.4 of TS 25.433, v.12.0.0or later. In such an example the Abnormal Conditions may be adapted asfollows:

If the RADIO LINK RECONFIGURATION REQUEST message does not contain theE-DCH Decoupling Indication IE but contains the HS-PDSCH RL ID IE and/orthe Serving E-DCH RL IE, and if both HS-DSCH and E-DCH are configured inthe new configuration but the Serving HS-DSCH Radio Link and the ServingE-DCH Radio Link are not in the same cell, then the Node B shall rejectthe procedure using the RADIO LINK RECONFIGURATION FAILURE message.

According to another embodiment, there is provided a method comprisingthe steps of inserting an information element into a radio link message,the information element comprising an indication that an uplink enhanceddedicated channel, E-DCH, may be decoupled from a high speed downlinkshared channel, HS-DSCH. The information element may be inserted in oneor more of a radio link setup request message, a radio link additionrequest message, a radio link reconfiguration prepare message or a radiolink reconfiguration request message.

As described with respect to FIGS. 1 above, embodiments of network 100may include one or more wireless devices 110, and one or more differenttypes of network nodes capable of communicating (directly or indirectly)with wireless devices 110. Examples of the network nodes include radionetwork nodes 115, 120, and core network nodes 130. The network may alsoinclude any additional elements suitable to support communicationbetween wireless devices 110 or between a wireless device 110 andanother communication device (such as a landline telephone).

Wireless device 110, radio network node 115, and core network node 130may use any suitable radio access technology, such as long termevolution (LTE), LTE-Advanced, UMTS, HSPA, GSM, cdma2000, WiMax, WiFi,another suitable radio access technology, or any suitable combination ofone or more radio access technologies. For purposes of example, variousembodiments may be described within the context of certain radio accesstechnologies, such as WCDMA. However, the scope of the disclosure is notlimited to the examples and other embodiments could use different radioaccess technologies.

Each of wireless device 110, radio network node 115, radio networkcontroller 120, and core network node 130 may include any suitablecombination of hardware and/or software. Examples of particularembodiments of a radio network node 115, for example a radio basestation, and network nodes (such as radio network controller 120 or corenetwork node 130) are described with respect to FIGS. 5 and 6 below,respectively.

FIG. 5 is a block diagram illustrating certain embodiments of a radionetwork node 115. Examples of radio network node 115 include an eNodeB,a node B, base station node, a wireless access point (e.g., a Wi-Fiaccess point), a low power node, a base transceiver station (BTS),transmission points, transmission nodes, remote RF unit (RRU), remoteradio head (RRH), a drifting radio network controller (DRNC) etc. Radionetwork nodes 115 may be deployed throughout network 100 as a homogenousdeployment, heterogeneous deployment, or mixed deployment. A homogeneousdeployment may generally describe a deployment made up of the same (orsimilar) type of radio network nodes 115 and/or similar coverage andcell sizes and inter-site distances. A heterogeneous deployment maygenerally describe deployments using a variety of types of radio networknodes 115 having different cell sizes, transmit powers, capacities, andinter-site distances. For example, a heterogeneous deployment mayinclude a plurality of low-power nodes placed throughout a macro-celllayout. Mixed deployments may include a mix of homogenous portions andheterogeneous portions.

Radio network node 115 may include one or more of transceiver 510,processor 520, memory 530, and network interface 540. In someembodiments, transceiver 510 facilitates transmitting wireless signalsto and receiving wireless signals from wireless device 510 (e.g. via anantenna), processor 520 executes instructions to provide some or all ofthe functionality described above as being provided by a radio networknode 115, memory 530 stores the instructions executed by processor 520,and network interface 540 communicates signals to backend networkcomponents, such as a gateway, switch, router, Internet, Public SwitchedTelephone Network (PSTN) I core network nodes 130, radio networkcontrollers 120, etc.

Processor 520 may include any suitable combination of hardware andsoftware implemented in one or more modules to execute instructions andmanipulate data to perform some or all of the described functions ofradio network node 115. In some embodiments, processor 520 may include,for example, one or more computers, one or more central processing units(CPUs), one or more microprocessors, one or more applications, and/orother logic.

Memory 530 is generally operable to store instructions, such as acomputer program, software, an application including one or more oflogic, rules, algorithms, code, tables, etc. and/or other instructionscapable of being executed by a processor. Examples of memory 530 includecomputer memory (for example, Random Access Memory (RAM) or Read OnlyMemory (ROM)), mass storage media (for example, a hard disk), removablestorage media (for example, a Compact Disk (CD) or a Digital Video Disk(DVD)), and/or or any other volatile or non-volatile, non-transitorycomputer-readable and/or computer-executable memory devices that storeinformation.

In some embodiments, network interface 540 is communicatively coupled toprocessor 520 and may refer to any suitable device operable to receiveinput for radio network node 115, send output from radio network node115, perform suitable processing of the input or output or both,communicate to other devices, or any combination of the preceding.Network interface 540 may include appropriate hardware (e.g., port,modem, network interface card, etc.) and software, including protocolconversion and data processing capabilities, to communicate through anetwork.

Other embodiments of radio network node 115 may include additionalcomponents beyond those shown in FIG. 5 that may be responsible forproviding certain aspects of the radio network node's functionality,including any of the functionality described above and/or any additionalfunctionality (including any functionality necessary to support thesolution described above). The various different types of radio networknodes may include components having the same physical hardware butconfigured (e.g., via programming) to support different radio accesstechnologies, or may represent partly or entirely different physicalcomponents.

According to one embodiment there is provided a radio network node 115,for example a base station or Node B or DRNC, for decoupling an uplinkenhanced dedicated channel, E-DCH, and a high speed downlink sharedchannel, HS-DSCH. The radio network node 115 comprises a networkinterface 540 adapted to interface with a radio network, a memory unit530, and a processor unit 520 adapted to run program instructions storedon the memory unit 530. The processor unit 520 is adapted to determinewhether a radio link message received from a radio network controller,RNC, contains an indication that a radio link procedure has thecapability of decoupling are E-DCH and a HS-DSCH. Where it is determinedthat the radio link message does not contain an E-DCH indication, theprocessor unit 520 is further adapted to reject the radio link procedurein the event that a serving E-DCH radio link and a serving HS-DSCH radiolink are not configured in the same cell.

In one example, where it is determined that the radio link message doescontain an E-DCH indication, the processor unit 520 may be furtheradapted to not reject the radio link procedure in the event that aserving E-DCH radio link and a serving HS-DSCH radio link are notconfigured in the same cell.

According to some embodiments a radio link procedure may comprise aradio link setup request procedure, a radio link addition requestprocedure, a radio link reconfiguration prepare procedure or a radiolink reconfiguration request procedure.

According to some embodiments a radio link message may comprise a radiolink setup request message, a radio link addition request message, aradio link reconfiguration prepare message or a radio linkreconfiguration request message.

FIG. 6 is a block diagram illustrating certain embodiments of a radionetwork controller 120 or core network node 130. Examples of networknodes can include a mobile switching center (MSC), a serving GPRSsupport node (SGSN), a mobility management entity (MME), a radio networkcontroller (RNC), a base station controller (BSC), and so on. Thenetwork node includes processor 620, memory 630, and network interface640. In some embodiments, processor 620 executes instructions to providesome or all of the functionality described above as being provided bythe network node, memory 630 stores the instructions executed byprocessor 620, and network interface 640 communicates signals to asuitable node, such as a gateway, switch, router, Internet, PublicSwitched Telephone Network (PSTN), radio network nodes 115, radionetwork controllers 120, core network nodes 130, etc.

Processor 620 may include any suitable combination of hardware andsoftware implemented in one or more modules to execute instructions andmanipulate data to perform some or all of the described functions of thenetwork node. In some embodiments, processor 620 may include, forexample, one or more computers, one or more central processing units(CPUs), one or more microprocessors, one or more applications, and/orother logic.

Memory 630 is generally operable to store instructions, such as acomputer program, software, an application including one or more oflogic, rules, algorithms, code, tables, etc. and/or other instructionscapable of being executed by a processor. Examples of memory 630 includecomputer memory (for example, Random Access Memory (RAM) or Read OnlyMemory (ROM)), mass storage media (for example, a hard disk), removablestorage media (for example, a Compact Disk (CD) or a Digital Video Disk(DVD)), and/or or any other volatile or non-volatile, non-transitorycomputer-readable and/or computer-executable memory devices that storeinformation.

In some embodiments, network interface 640 is communicatively coupled toprocessor 620 and may refer to any suitable device operable to receiveinput for the network node, send output from the network node, performsuitable processing of the input or output or both, communicate to otherdevices, or any combination of the preceding. Network interface 640 mayinclude appropriate hardware (e.g., port, modem, network interface card,etc.) and software, including protocol conversion and data processingcapabilities, to communicate through a network.

According to one embodiment, there is provided a radio networkcontroller, RNC, node 120 for decoupling an uplink enhanced dedicatedchannel, E-DCH, and a high speed downlink shared channel, HS-DSCH. Theradio network controller node 120 comprises a network interface 640adapted to interface with a radio network, a memory unit 630, and aprocessor unit 620 adapted to run program instructions stored on thememory unit. The processor unit 620 is adapted to determine whether areceived radio link message contains a E-DCH decoupling indication,indicating that a base station node supports decoupling of are E-DCH anda high speed downlink shared channel. Where it is determined that theE-DCH decoupling indication has not been received, the processor unit620 is further adapted to control the base station node to reject theradio link procedure in the event that a serving E-DCH radio link and aserving HS-DSCH radio link are not configured in the same cell.

In one example, where it is determined that the E-DCH decouplingindication has been received, the processor unit 620 may be furtheradapted to control the base station node to not reject the radio linkprocedure in the event that a serving E-DCH radio link and a servingHS-DSCH radio link are not configured in the same cell.

According to some embodiments a radio link procedure may comprise aradio link setup request procedure, a radio link addition requestprocedure, a radio link reconfiguration prepare procedure or a radiolink reconfiguration request procedure.

According to some embodiments a radio link message may comprise a radiolink setup request message, a radio link addition request message, aradio link reconfiguration prepare message or a radio linkreconfiguration request message.

Other embodiments of the network node may include additional componentsbeyond those shown in FIG. 6 that may be responsible for providingcertain aspects of the network node's functionality, including any ofthe functionality described above and/or any additional functionality(including any functionality necessary to support the solution describedabove).

SUMMARY OF EXAMPLE IMPLEMENTATION

From the above it can be seen that, in particular exampleimplementations, the proposed solutions may provide methods fordecoupling an E-DCH cell and a HS-DSCH cell that solves the backwardsnot compatible problem. In one example embodiment, the method mayinclude:

Determining whether a radio link message contains a E-DCH decouplingindication, and where it is determined that the radio link message doesnot contain an E-DCH decoupling indication, a base station node iscontrolled to reject a radio link procedure in the event that a servingE-DCH radio link and a serving HS-DSCH radio link are not configured inthe same cell.

Where it is determined that the radio link message does contain an E-DCHdecoupling indication, a base station node is controlled such that itdoes not reject a radio link procedure in the event that a serving E-DCHradio link and a serving HS-DSCH radio link are not configured in thesame cell.

In another embodiment, the method comprises determining whether an RNChas received an indication stating that a Node B or DRNC supports EDCHdecoupling;

Applying pre Rel-12 Abnormal Conditions, where it is determined that theindication has not been received from the Node B or DRNC; and

Not applying pre Rel-12 Abnormal Conditions, where it is determined thatthe indication has been received from the Node B or DRNC.

Optionally, the indication from Node B may be set on Cell bases and beincluded in Audit and Resource Status Indication procedure.

Optionally, the indication from Node B may be added to existing Node BCell Capability Container, which is sent in AUDIT.

In another example embodiment, the method may include:

Determining whether an RNC has transmitted a message to the Node B orDRNC indicating that the radio link is setup with decoupled E-DCH andthe Node B or DRNC has accepted to support E-DCH decoupling;

Applying pre Rel-12 Abnormal Conditions, where it is determined that theRNC has not transmitted the message to the Node B or DRNC indicatingthat the radio link is setup with decoupled E-DCH and/or the Node B orDRNC has not accepted to support E-DCH decoupling; and

Not applying pre Rel-12 Abnormal Conditions, where it is determined thatRNC has transmitted the message and the Node B or DRNC has accepted tosupport E-DCH decoupling.

In still another example embodiment, the method may include:

Determining whether 1) an RNC has transmitted a message to the Node B orDRNC indicating that the radio link is setup with decoupled E-DCH and 2)the Node B or DRNC has transmitted an indication stating that the Node Bor DRNC supports E-DCH decoupling;

Applying pre Rel-12 Abnormal Conditions, where it is determined that theRNC has not transmitted the message to the Node B or DRNC and that theNode B or DRNC has not transmitted the message indicating that itsupports E-DCH decoupling; and

Not applying pre Rel-12 Abnormal Conditions, where it is determined thatthe RNC has transmitted the message to the Node B or DRNC and that theNode B or DRNC has transmitted the message indicating that it supportsE-DCH decoupling.

Other implementations may include a wireless communication device and/oraccess node configured to implement the described method, or a wirelesscommunication system in which a wireless communication device and/oraccess node implement the described method.

Some embodiments of the disclosure may provide one or more technicaladvantages. For example, in certain embodiments, decoupling of theserving E-DCH cell and the serving HS-DSCH cell may be allowed for theimproved performance in the presence of imbalance between the uplink andthe downlink. Accordingly, a technical advantage may be the decouplingof the serving E-DCH cell and the serving HSDSCH cell in heterogeneousnetwork environments. Another technical advantage may be that the Node Bor DRNC will not reject the decoupling procedure even where the HS-DSCHand the E-DCH are not the same cell. Still another advantage may be thatthe backwards not compatible problem may be alleviated.

Some embodiments may benefit from some, none, or all of theseadvantages. Other technical advantages may be readily ascertained by oneof ordinary skill in the art.

Modifications, additions, or omissions may be made to the systems andapparatuses disclosed herein without departing from the scope of theinvention. The components of the systems and apparatuses may beintegrated or separated. Moreover, the operations of the systems andapparatuses may be performed by more, fewer, or other components.Additionally, operations of the systems and apparatuses may be performedusing any suitable logic comprising software, hardware, and/or otherlogic. As used in this document, “each ” refers to each member of a setor each member of a subset of a set.

Modifications, additions, or omissions may be made to the methodsdisclosed herein without departing from the scope of the invention. Themethods may include more, fewer, or other steps. Additionally, steps maybe performed in any suitable order.

Although this disclosure has been described in terms of certainembodiments, alterations and permutations of the embodiments will beapparent to those skilled in the art.

Accordingly, the above description of the embodiments does not constrainthis disclosure. Other changes, substitutions, and alterations arepossible without departing from the spirit and scope of this disclosure,as defined by the following claims.

Although the embodiments described above are made in the context ofAbnormal Conditions for a Radio Link Setup procedure, it is noted thatthe method may also be used of other radio link procedures, such asradio link addition, radio link reconfiguration, as shown in theexamples above.

It should be noted that the above-mentioned embodiments illustraterather than limit the invention, and that those skilled in the art willbe able to design many alternative embodiments without departing fromthe scope of the appended claims. The word “comprising” does not excludethe presence of elements or steps other than those listed in a claim,“a” or “an” does not exclude a plurality, and a single processor orother unit may fulfil the functions of several units recited in theclaims. Any reference signs in the claims shall not be construed so asto limit their scope.

1. A method in a network node for decoupling an uplink enhanceddedicated channel, E-DCH, and a high speed downlink shared channel,HS-DSCH, the method comprising: determining whether a radio link messagecontains a E-DCH decoupling indication and where it is determined thatthe radio link message does not contain an E-DCH decoupling indication,rejecting a radio link procedure in the event that a serving E-DCH radiolink and a serving HS-DSCH radio link are not configured in the samecell.
 2. A method as claimed in claim 1, comprising: where it isdetermined that the radio link message does contain an E- DCH decouplingindication, controlling a base station node such that it does not rejecta radio link procedure in the event that a serving E-DCH radio link anda serving HS-DSCH radio link are not configured in the same cell.
 3. Amethod as claimed in claim 1, wherein the E-DCH decoupling indication isprovided in an information element of the radio link message.
 4. Amethod as claimed in claim 1, wherein the E-DCH decoupling indication isset on a per cell basis.
 5. A method as claimed in claim 1, wherein theE-DCH decoupling indication is included in an audit and resource statusindication procedure.
 6. A method as claimed in claim 1, wherein theE-DCH decoupling indication is added to a cell capability container. 7.A method as claimed in claim 1, wherein the network node comprises aNode B or a drifting radio network controller, DRNC, node.
 8. A methodas claimed in claim 1, wherein: a radio link procedure comprises a radiolink setup request procedure, a radio link addition request procedure, aradio link reconfiguration prepare procedure or a radio linkreconfiguration request procedure; and/or a radio link message comprisesa radio link setup request message, a radio link addition requestmessage, a radio link reconfiguration prepare message or a radio linkreconfiguration request message.
 9. A method as claimed in claim 8,wherein the method comprises performing abnormal conditions relating toone or more of sections 8.2.17.4 or 8.3.1.4 or 8.3.2.4 or 8.3.5.4 of thethird generation partnership project, 3GPP, technical specification25.433 version 12.0.0 or later.
 10. A method as claimed in claim 1,wherein the network node comprises a radio network controller, RNC,node.
 11. A method as claimed in claim 10, wherein the E-DCH decouplingindication is received from a base station node.
 12. A method as claimedin claim 1, wherein the network node comprises a base station node. 13.A method as claimed in claim 12, wherein the E-DCH decoupling indicationis received from a radio network controller, RNC node.
 14. A method asclaimed in claim 12, wherein the base station node further comprises thestep of deciding whether or not to support E-DCH decoupling.
 15. Amethod as claimed in claim 14, wherein the step of deciding whether ornot to support E-DCH decoupling is based on one or more of: whether thebase station node is capable of supporting decoupling of an E-DCH and aHS-DSCH; or whether the base station node is capable of supportingdecoupling of an E-DCH and a HS-DSCH, and if so, whether the basestation node wishes to provide decoupling for that particular radio linkbased on some other criteria; whether the base station node is capableof supporting decoupling of an E-DCH and a HS-DSCH, and if so, whetherthe base station node has capacity to support E-DCH decoupling.
 16. Aradio network node for decoupling an uplink enhanced dedicated channel,E-DCH, and a high speed downlink shared channel, HS-DSCH, the radionetwork node comprising: a network interface (540) adapted to interfacewith a radio network; a memory; a processor adapted to run programinstructions stored on the memory; wherein the processor is adapted todetermine whether a radio link message received from a radio networkcontroller, RNC, contains an indication that a radio link procedure hasthe capability of decoupling an E-DCH and a HS-DSCH; and, where it isdetermined that the radio link message does not contain an E-DCHindication, the processor is further adapted to reject the radio linkprocedure in the event that a serving E-DCH radio link and a servingHS-DSCH radio link are not configured in the same cell.
 17. A radionetwork node as claimed in claim 16 whereby, where it is determined thatthe radio link message does contain an E-DCH indication, the processoris further adapted to not reject the radio link procedure in the eventthat a serving E-DCH radio link and a serving HS-DSCH radio link are notconfigured in the same cell.
 18. A radio network controller, RNC, nodefor decoupling an uplink enhanced dedicated channel, E-DCH, and a highspeed downlink shared channel, HS-DSCH, the radio network controllernode comprising: a network interface adapted to interface with a radionetwork; a memory; a processor adapted to run program instructionsstored on the memory; wherein the processor is adapted to determinewhether a received radio link message contains a E-DCH decouplingindication, indicating that a base station node supports decoupling ofan E-DCH and a high speed downlink shared channel, HS-DSCH; and where itis determined that the E-DCH decoupling indication has not beenreceived, the processor is further adapted to reject the radio linkprocedure in the event that a serving E-DCH radio link and a servingHS-DSCH radio link are not configured in the same cell.
 19. A radionetwork controller, RNC, node as claimed in claim 18 wherein, where itis determined that the E-DCH decoupling indication has been received,the processor is further adapted to control the base station node to notreject the radio link procedure in the event that a serving E-DCH radiolink and a serving HS-DSCH radio link are not configured in the samecell.
 20. A method comprising the steps of inserting an informationelement into a radio link message, the information element comprising anindication that an uplink enhanced dedicated channel, E-DCH, may bedecoupled from a high speed downlink shared channel, HS-DSCH.
 21. Amethod as claimed in claim 20, wherein the information element isinserted in one or more of a radio link setup request message, a radiolink addition request message, a radio link reconfiguration preparemessage or a radio link reconfiguration request message.